Closed Bug 1187104 Opened 10 years ago Closed 10 years ago

[gtk3] [mulet] REFTEST TEST-UNEXPECTED-FAIL | file:///home/worker/build/tests/reftest/tests/layout/reftests/xul/tree-row-outline-1.xul | image comparison (==), max difference: 229, number of differing pixels: 323

Categories

(Core :: Widget: Gtk, defect)

Product:
Core
Component:
Widget: Gtk
Platform:
Unspecified
Linux
Type:
defect
Priority:
Not set
Severity:
normal

Tracking

()

Status:
RESOLVED WORKSFORME

People

(Reporter: glandium, Unassigned)

References

Details

(Keywords: regression)

Blocks: ship-gtk3
Keywords: regression
OS: Unspecified → Linux
No longer blocks: ship-gtk3
The timeouts are, somehow, gone. There's now a perma-orange: http://hg.mozilla.org/mozilla-central/raw-file/tip/layout/tools/reftest/reftest-analyzer.xhtml#logurl=https://queue.taskcluster.net/v1/task/WUvZtBT1TMuf84CLFL3SQw/runs/0/artifacts/public/logs/live_backing.log&only_show_unexpected=1 There is a one pixel difference in the vertical position of the second line of text in the test case. The weird thing is that it only happens on mulet builds, not on browser builds for the same changeset.
Summary: [gtk3] Reftest timeouts on mulet builds → [gtk3] [mulet] REFTEST TEST-UNEXPECTED-FAIL | file:///home/worker/build/tests/reftest/tests/layout/reftests/xul/tree-row-outline-1.xul | image comparison (==), max difference: 229, number of differing pixels: 323
This is already annotated with "skip-if((B2G&&browserIsRemote)||Mulet)", so I don't know why this is running. It should be fails-if(Mulet) if not intermittent. I wonder whether Mulet and browser builds use different fonts.
The problem is that the reftest harness doesn't handle multiple things correctly (bug 720684). Fixed in https://hg.mozilla.org/integration/mozilla-inbound/rev/f37c01f7c064
Status: NEW → RESOLVED
Closed: 10 years ago
Resolution: --- → WORKSFORME
You need to log in before you can comment on or make changes to this bug.